For someone just starting into Pinegrow (bought Pro version this week), what advantages does Atom bring over just using the code editor built into Pinegrow?
While not code-phobic, I am code-nooby. (Just now doing W3 html and css tutorials - head is spinning). So would adding Atom to the mix introduce more confusion than it is worth at this time? Or is there something that Atom offers to make it worth the extra effort?
Thanks droidgoo. Appreciate the full and very helpful report.
I’m starting to think that adding a separate text editor will have to come later for me, seeing as I’m quite overwhelmed already with all the new stuff I am learning. I stand before a vast jungle, thinking, “Holy smokes where do I even start?” I think I’ll have my hands full for a while just trying to use Pinegrow, the one machete I’ve got. To try two-handed chopping is beyond my current talent level. But I’ll keep chopping. Hope to eventually work through to a clearing where I can see the sky again. Maybe then I’ll take a breather before I try adding a new tool. Thanks again. Appreciate ya.
While the attitude is excellent, I miss in all those “advantage/disadvantage” discussions about apps a way more fundamental discussion which is:
“Am I enough prepared and organised for starting into the code world?”
The answer to this is mostly: “No - not at all”
The key into a successful and not so overwhelming start is literally content. Text written, such as a tiny business-plan for an existing (or even a imaginary one - such as the butcher next door) is inevitable.
You’re asking me why?
Excellent question! Because it helps you understanding the very basics of front-end dev, called HTML (five at the date of writing). How do I like to structure my text. What is a heading e.g. This avoids some nonsense statement such as “the limitation of headings” I picked up recently in another thread of this board.
Believe it or not: The inevitable thing in web is HTML - all the rest is theoretically mandatory.
All (nearby) elements are reachable within the library of PG (one of those strengths of PG). Start slow - make yourself clear what the essential elements are (header, main, footer, aside, paragraph, h1-h6, div) and what semantic/or non-semantic role they’re playing.
Certainly this structure doesn’t look quite well - however it is allowing you to see a logic within your lil storyboard. Ask something like: Who is doing what for whom and how and where and you have a logic structure to follow. It is semantically structured - not really visually. That’s then the next step: positioning and displaying the things as you want it. I invested a good year into it (back in the days of relative/absolute/float/clear) - which has been substituted by flex (grid).
I could add much more, but I hope you got the gist: Divide the monster into smaller chunks. As the Chinese saying: “If you are in a hurry, walk slow!”
Personally I think, that an app is not a question of advantage, it’s a question of convenience and experience. We’re building one web and all apps are doing a least one and the same thing. Nothing more, nothing less.
Your point is well taken, Thomas. HTML is king. I’m trying hard to catch up. Taking every tutorial I find, mostly found on this board. And there’s some great ones being recommended. It’s just overwhelming right now, and my questions are all so basic. But it’s coming along. I’ll get there. Meanwhile, to quote an old joke, it keeps me “busier than a one-legged man in an ass-kicking contest”.
This board is super helpful. (Both for keeping me busy, and for teaching me stuff. Each question answered generates another question.)
Dumy question about using this board: Can someone please point me to a tutorial (I couldn’t find it in the faqs) on how to do basic things like:
flag someones name with that little grey box
when specifying a website, it comes up in a box
Stuff like that. Yeah, I know, basic.
Learnin’! (never done a board before)
also, if you use the @ symbol, then write their name… it should auto select their name as you type part of it.
and , if you get to the stage where you want to post bits of code, this is handy:-
and as for the actual topic, advantage of …etc,
there are a pile of text editors!
free and paid.
the topic of many flame wars
Find one you like (obviously, there are the chosen new kids on the block) and play with it.
The pinegrow Text editor is pretty good, but its just a basic editor. and lacks some features (like a lot that the big editors can do)
But, instead of spending AN AGE…developing the dogs danglies of text editors…which is a monumental task itself, they have opted to plugin to already existing, incredibly powerful FREE editors.
These can do a pile of other stuff like, project wide find and replace, refactoring (changing the name of something , EVERYWHERE, in the file or project if you so wish) multi cursor edits (edit in several place at the same time… spooky (first appeared with SublimeText btw… hint)
and shedloads of other stuff.
and they have OTHER plugins, for life reloading of browsers as you type (which PineGrow does anyway) and all sorts of magic.
So play with a text editor and find some tutorials on it, setting it up, adding the necessary plugs for say, web development etc etc and just tinker.
While doing the PG thing and learning all that jazz.
then connect them and just carry on doing the content and code side in that, see how it goes and if its for you and if you really need it.
You can get A LOT done with the PG text editor, but it all comes down to workflow.
If you end up using a text editor for other things too, (prose, other languages etc) then you will end up using all its shortcuts for speed and adding plugins to add functionality and your speed picks up.
You will then miss these, when you go back to the basic PG editor.
So you use it WITH PG , via the plugin and Tada! you dont miss a beat, you just carry on as normal, without missingstuff that your used to doing.
And loathe as I am to endorse Microsoft for anything, their editor is ok (read, **Pretty fantastic for a free product - if it was a paid product it would be mint too!) and it seems less laggy than Atom… which had some performance issues… and since MS now OWNS Github (spits!) - which produced the Atom Editor, AND… MS has already released VSCode… there is one obvious outcome.
Of course, MS says they will continue the BOTH Editors …and NOT drop Atom…ever…in favour of their own VSCode editor, to keep both camps happy …however that seems highly unlikely considering
So… You might wish to check out a different editor for PG Plugin support (hint, VSCode - while we wait for a SublimeText plugin …ooh! yet another hint maybe? :). )
were you employing some form of accessibility tools for the partial sighted…totally blind?
just to annoy you…>
When your scribbling in the window on the left… your output in the forum, should appear in the window on the right. Just check to see if you mangled something in your original post.
…ie, after your post, click the little pencil icon underneath it and then you can edit your original post… fiddle with your link, copy and paste it again and see if you have missed a little something.
also, do you know that there. is a Slack channel for PG too?
ideally this is more for real time conversational support, but tbh, it doesnt really work that way, unless you pair up with someone to chat with them on there as it can be rather quiet/delayed.
but…ive not been on it for aaaages, but it can be quite exciting to be connected when doing this sort of learning stuff,
Also, again, … I have just started to experiment with the VSCode… Live plugin ecosystem.
that is, it has in app commmunication for code sharing!
instant messaging and
so you can share your code/repository,
text chat to someone
speak to them at the same time.
that is pretty spectacular>
of course that’s because they want everyone to share their code… store it on GitHub
Just going to swim to my truck to get my external hard drives…in case it dissolves.
…I hope the roof is made of sterner stuff
All good and WOW. that took me 15 mins to get there and back and plug in
an external HDD.
I really must try harder
But anyway, with pinegrow,
learn that, tinkering about, play with the draggy droopy stuff, learn the interface, its quirks
HOW TO USE THE CSS panels.
there are two, one for Frameworks (aka Bootstrap… use this FIRST to adjust BS things)
then, if it just cant get your BS things to where you want them,
use the CSS Editor panel to style stuff more radically - and store them in an external CSS sheet.
NEVER modify the original BS style sheets… worlds of pain await, when you update stuff if this is done.
and , play with PG’s native text editor.
If it does everything you want at this level , GREAT! just carry on with it.
Also play with some text editors.
write code in PG, write the same code in the Text editors, play with their color themes, change fonts, line spacing, all sorts of environment stuff,
then as you learn more you will try and do more.
things that then speed up your coding like emmet - its a plugin that adds rocketesque speed ninja coding skills. -but PG text editor has PUG …which Ive never used.
So just been looking it up and OH! its not a short hand …thing.
Its a templating engine…er ok… and it was formally known as Jade
…umm ok again
have a foreigner to explain.
there are lots of them/us about
so, pug and Emmet (the former is an awesome html short hand that you can add plugins in your editors of choice ot accomplish) I always wished for this in PG, but, the external text editors can use it via plugins.
SublimeText has a nice one
ps…>Ive been struggling to find any decent docs on PUG
but here’s something