CSS Conic-Gradients

[Nancy OShea]

I see endless possibilities with this new CSS specification.

3.3. Conic Gradients:

But the only browser currently supporting it is Chrome.  

https://caniuse.com/#feat=css-conic-gradients

Good news for developers, there is a polyfill.

CSS conic-gradient() polyfill

[pziecina]

osgood_  wrote

Yeah but even though lm pretty good at all the languages you mention lm still not in that kind of league to be able to create the types of applications l think you are talking about.........theres php and theres php on another level thats all lm implying

I don't think any single person can create what I am talking about, there is simply too much specialised knowledge involved. I do think that it should be possible though for a single developer to do a lot of it though, the problem I see is with clients and ide's, as selling such an application to clients requires a modular 'progressive' development, and ide's such as Dw and many others simply do not support modular 'progressive' development in any easily managable way.

Time required also come into it, as I previously said, I have worked on what I do for 16 years, and the application is constantly evolving. For a self employed person though it is probably not viable unless one is looking long term anyway.

[osgood_]

Thats exactly why l said l think it requires  knowledge over and above the skills of a front end developer and a back end developer who can put a simple crud app together, which make up the majority of websites. The reason why l wont be moving into that arena or attempting to because l do not have the time or reason given the kind of clients l represent.

On another note totally disconnected  - how does anyone type on a tablet device, every other word is complete garbage and l have to go back and correct it. Maybe l should use one of those stick things.

[pziecina]

osgood_  wrote

On another note totally disconnected  - how does anyone type on a tablet device, every other word is complete garbage and l have to go back and correct it. Maybe l should use one of those stick things.

Do the same as I do, turn off auto-completion and auto-suggestion. You have to read through what you write, and highlight any words you think are miss-spelt by tapping on them, (suggestions should then be shown) and you will still get words and grammar wrong, (don't worry about it, I don't).

[osgood_]

I think its more to fo with the keyboard pafs being too closr togethrr snd habing a fst finger, which l havent got. I deliberatly left the dpelling uncortecyed in yhis podt....lol hope you can decipher it

[Nancy OShea]

Related post

https://forums.adobe.com/message/10677370?tstart=0#10677370

[pziecina]

osgood_  wrote

Can either of you provide some url  examples of thrse PWAs because l have no idea what they look like or if l have ever come across any......most websites l visit just look like websites to me and don't do anything that special other than show a bit of information. About the most complex offering l've come across is a calculator.

I would be very surprised if anyone can direct you to one you can use. The problem with browser based web applications is that they are targeted at specific groups. I work on one that is specificly targeted at aerospace, and I think Birnou works on one targeted at the medical profession.

Both require log-in, authorisation to use (before you even get a user name and password) and more often than not, you must be a member of that profession with clearances. You may not think of Banking apps as requirering such user criteria, but if you think about it, all the above apply to some extent even to those.

People who work on such browser based apps, (or native apps) are more than likely subject to none disclosure, (would you have temp staff working on such apps?) but are compensated by better job security and a staff position.

This is also why I think that the inovation such apps create, takes years to filter down to the 'run of the mill' web designer, and why knowing code is not enough. One must also have the ability for 'idea creation', and never just rely on what everyone else is doing, or accept the conception that it is not possible, just because browsers do not all support a feature, or because others say so.

[osgood_]

So these PWAs arent replacing the traditional website its just another discipline as far as l can make out from the short clips and sound bytes l've been listening to. Must be because the few layout examples that l have seen look too simple to be websites.

As lve only got a couple of years left l dont really want to be expending enormous amounts of time learning something that has limited exposure as far as how it can benefit the kind of clients l work for. Sure an app sounds good but if it means writing something independent of a traditional website workflow lm not so sure my clients would be interesred in splashing the cash.

[pziecina]

osgood_  wrote

So these PWAs arent replacing the traditional website its just another discipline as far as l can make out from the short clips and sound bytes l've been listening to. Must be because the few layout examples that l have seen look too simple to be websites.

As lve only got a couple of years left l dont really want to be expending enormous amounts of time learning something that has limited exposure as far as how it can benefit the kind of clients l work for. Sure an app sounds good but if it means writing something independent of a traditional website workflow lm not so sure my clients would be interesred in splashing the cash.

Forget the device specific apps that most produce, they are often just versions of the traditional website, and not worth the trouble. If you have an iPad look at things like 'Pages' and the Coda app.

Also think of what you would require to move a traditional large computer program adapted to match the clients overall requirerments to the web. That includes stock control, all reference material, animations of component assembly, parts catalogue,  booking systems, client and product records, then add anything else you can think of.

[Nancy OShea]

pziecina  wrote

I would be very surprised if anyone can direct you to one you can use. The problem with browser based web applications is that they are targeted at specific groups.

Right.  Invitations, log-ins and security layers are mandatory.  So I can't post an actual example that you could view.

But consider a typical use case.  You get a replacement credit card in the mail.  The card label says, "activate this before using it by going to our website. "   The special URL asks for the activation code on your card.  Then it asks you to log-in with your username and password.  Then the app sends a text message to your mobile phone with a 6 digit verification code that you must enter to proceed.   Once verified, you get confirmation that your card has been activated and they invite you to do other things like update personal info, check your FICO scores, set-up automatic bill pay, etc.... 

[B i r n o u]

Yes, but this kind of scenario can happen whether it is a traditional website or a pwa... on the pwa side this is really what happens under the hood that differs and the javascript api that are used.

[pziecina]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

... on the pwa side this is really what happens under the hood that differs and the javascript api that are used.

You could do it with a traditional web site, but then it would not be worth while, because at some point it would be necessary for the user to log-in, and at that point it becomes closed to unauthorised users.

Lets be honest the really interesting 'stuff' for users would be in the secure section, and not open to the general public.

[Nancy OShea]

https://forums.adobe.com/people/B+i+r+n+o+u  wrote

Yes, but this kind of scenario can happen whether it is a traditional website or a pwa... on the pwa side this is really what happens under the hood that differs and the javascript api that are used.

Yes, I know.  But the old websites were prone to many failures.  And I can tell immediately by the response rate that it's a PWA.   Everything is fast and seamless. 

[osgood_]

But that is just all backend stuff which has been around for donkies years. My electric and gas company uses an app to show me how much energy lve used in a particular peroid. I dont consider that kind of app something that a front end developer specialises in. I think what is being implied is that we are moving away from traditional websites to PWAs. The way l see it is the PWA is a drastically reduced version of the full website and may be useful for small sound bytes when you are offline and want to read news which is 4 weeks old.

[pziecina]

osgood_  wrote

The way l see it is the PWA is a drastically reduced version of the full website and may be useful for small sound bytes when you are offline and want to read news which is 4 weeks old.

notice that I always say browser based applications, not PWA.

Nancy used the term 'progressive web application' which can be applied to both browser based and device specific applications, but the difference can be dramatic, as when online a browser based web application has very few limitations in terms of what is now possible, everything that any browser implements is open for use.

[osgood_]

pziecina  wrote

osgood_   wrote

The way l see it is the PWA is a drastically reduced version of the full website and may be useful for small sound bytes when you are offline and want to read news which is 4 weeks old.

notice that I always say browser based applications, not PWA.

Well you just cleared up what l was thinking..........who makes up this stupid buzz word terminology which noone has any idea of what it means......WTF is a push notification............its all crap, smoke and mirrors..........can anyone actually express anything anymore without talking a lot of dribble

[B i r n o u]

as can I second you on that one.. this book is marvelous... sorry I've just modified the link... liveBook