Someone works on it for a bit, then it's quiet then someone works on
it a bit, rinse repeat.
Andrew - I'm sure both Mark and Denny can give you pointers if you ask...
And I'd be all up for moving everything to GIT and getting rid of Trac
altogether...
If anyone wants to help in a 'non-coding' way - moving the wiki info
over to git (along with some housecleaning) would be a tremendous
help.
Jim
Sent from my mobile
MD
Sent from one of my many iDevices
MD
Sent from one of my many iDevices
Though it looks like people have already done this :)
https://github.com/adamcik/github-trac-ticket-import
https://gist.github.com/589126
It'd be tedious but might be worth a going through manually?
Or maybe import and then go through?
Jim
Jim
MD
Sent from one of my many iDevices
What's involved in moving it? Is it basically copy and paste pages,
and update links accordingly?
And what sort of housecleaning did you have in mind?
I'd probably be willing to help with either half of that, if someone
else wanted to take the other half.
Housecleaning would basically be... "is the info still relevant" and
could we improve it or just remove it.
Jim
Which I think leaves fixing links, importing images, and noting down
which pages could do with an update/etc.
So, if you want to turn on the GitHub wiki and/or give me relevant
permissions, I can probably get it done tonight or tomorrow. :)
If they are, they haven't mentioned it on this list nor the dev list.
So, if you're thinking of doing so yourself, I'd say go ahead. :)
I just submitted to the OpenBD list "if a CFEclipse dictionary xml file could be auto-generated with the nightly build like the documentation is."
The reply is they believe it is possible.
I'm off out shortly, but back in a few hours so can crack on with it then. :)
See: http://lists.parrot.org/pipermail/parrot-dev/2012-January/006525.html
--
Will "Coke" Coleda
http://perlbuzz.com/2012/01/parrot-tickets-now-converted-to-github.html
--
Will "Coke" Coleda
they shuttled him off to an undisclosed location.
I think it's called Albuquerque...
The initial version of the wiki import is now on GitHub. :)
There's still some tidying up to be done (I've already spotted several
links I need to fix, and there's no doubt other stuff), so I haven't
removed the "under construction" text yet. I'll be going through all
the pages again checking/fixing stuff later this evening (I'm off out
now).
Also, I've made a mental note of various housekeeping tasks that need
doing (e.g. updating images, better section organisation/structure,
improve wording, etc), and when I go through again I'll turn this into
an actual list, which I guess can then be added to the "Current Items
We Need Help With" section.
Jim
I've also added the various housekeeping tasks to this page:
https://github.com/cfeclipse/cfeclipse/wiki/How-You-Can-Contribute-To-CFEclipse
So anyone that wants to can pick on some of those issues to attack, or
of course work on anything else there that looks like it could do with
some polish. :)
A quick thing to remember: the wiki is itself powered by a Git repository.
So, for example, to add/modify images you do a `git clone
g...@github.com:cfeclipse/cfeclipse.wiki.git` and then you can commit
updated images as you would in a normal git repository, and once done
you `git push origin master` to get your changes live.
This also makes it easier to bulk edit files, or just for editing
larger files (which can be sluggish in the browser).
You can read more about it here:
https://github.com/blog/699-making-github-more-open-git-backed-wikis
Do they need to "parse" cfml internally?
Then bookmark this page and check it in a few months:
https://github.com/cfeclipse/cfeclipse/wiki/How-You-Can-Contribute-To-CFEclipse
:)
I think a fairer description would be that efforts floundered, due to
the inability/difficulty of expressing the complexity of CFML syntax
using ANTLR v3, which needed all these wacky "predicate" things to
determine what characters are special and when. (Most languages don't
have that problem; they are syntactically very simple.)
With ANTLR v4 things are done in an entirely different way - modal
grammars are supported (which makes predicates mostly/entirely
unnecessary). Without saying too much too soon, it basically means the
only roadblock is time. ;)
.pjf
--
Peter J. Farrell
pe...@mach-ii.com
p...@maestropublishing.com
http://blog.maestropublishing.com
Identi.ca / Twitter: @maestrofjp
Mark Drew
Mark Drew
That was only for cfscript, which of course is far closer to a
standard language.
Dunno what the status of that is though - I think it might be
somewhere on GitHub.
I'd love to be able to download a dump of his brain database and
upload it into mine ;-)
Yes and no.
See what Mark said about parsing - there's no use/benefit in even
asking the server to compile a page being edited - you pretty much get
a works/broken answer out of it, and an editor needs more than that.
For code insight, that is another thing Denny was investigating -
being able to connect to a running instance of a project and
automatically obtain extra information (e.g. mappings and custom tag
paths, variables which currently exist in scopes, and so on).
> For code insight, that is another thing Denny was investigating -
> being able to connect to a running instance of a project and
> automatically obtain extra information (e.g. mappings and custom tag
> paths, variables which currently exist in scopes, and so on).
I believe this is how ColdFusion Builder works, using the RDS server.
Of course that is specific to Adobe CF, however I did recently notice
a railo rds project on riaforge: http://railords.riaforge.org/. The
other thought I had is whether something like Colddoc could be used
for code insight. In a server agnostic way. It seems to allow
outputting in alternative formats and presumably you could use it
(either in real time or probably more likely as a "compile task") to
produce some kind of output format which could then be "queried" to
allow function and function argument completion from CFCs other than
the one you were working on.
The only problem is that once we start bringing in stuff like this, we
then need to have people set up servers stuff on their and configure
cfeclipse to point to it. So I do like the current approach where it
reads files from your project without further setup.
I did get a "proof of concept" working a couple of weeks ago which a
CFC and I think it's something that could be built upon...but it's
very much a work in progress at this stage and getting it working
properly really is going to depend on the parsing of the "currently
open file" to be modified as well. I submitted a pull request but I'm
not sure if it's made it into the dev builds yet. If anyone wants a
look let me know and I can provide a zip of the update site.
Andrew.
http://web-rat.com/blog/post.cfm/using-cfbuilder-with-railo
But from my experience it does require to have a server running, and
configured correctly to get it to work, even if it's not the RDS
component it's using.
There's a highly untested dev build out, sans a list of what's new. If
you can't wait to see things like outline/method view of cfscript-based
cfcs, and component assist (yes, we're not trapped in the currently open
CFC/dictionary anymore, thanks to Andrew and Mark!), feel free to give
it a spin!
The current implementation is geared towards Railo ATM, so it won't flag
missing semi-colons, and allows
for(var item in collection) { AndSomeOtherStuff() }
(the var'ed item would throw an error prior, and as such I don't think
it works in OpenBD, which is where the script parsing originated).
I'm hoping that what I did to the grammar wasn't /so/ horrible, and that
maybe OpenBD can use it, or get ideas from it, since I added bits to
parse "component { }" and ternary "if ? then : else" and a few other
things in there.
:DeN
--
Always remember you're unique, just like everyone else.
Can we get this from the update site, or do we need to build it ourselves?
I haven't seen any updates in github - is your intention to put them
into master or develop?
So happy to see you back and contributing to my favourite CF ide. I'm
using CFEclipse it as I type (well took a break from using it to type
this!). Actually just noted down a list of stuff to look at
surrounding my latest changes. In particular, function method
completion only works in .cfm files at the moment, and not cfc's,
which is where I need it most! I might try and figure that one out
this weekend.
Andrew.
> --
> For more information on CFEclipse visit: cfeclipse.org
> For support, FAQ and tips and tricks visit: https://github.com/cfeclipse/cfeclipse/wiki
As for git, I majorly fuxored up the merge some time ago, so, lemme see
if I can clean up git a bit, or maybe just push a new branch. Apologies
if the result messes up pulls!
Couple changes to this push:
Compromise on engines: Semicolons are required again, as two of the 3
CFML engines require them.
Support for Railo specific stuff like:
savecontent variable="wee" { writeOutput("woohoo"); }
is there though, so, fair's fair. :)
Eventually we'll split out the parsers or some such...
In general, I'd rather miss errors than have false errors.
Anywho, function method completion /should/ work in cfc's... maybe try
this latest build and see. I tried to hook up everything that had been
done for the tags, for the script equivs, but we really need a single
model (maybe just copy java's, with "compilationUnits" and whatnot) vs.
what we're rocking now (checking context, etc.).
Lemme see if I can get this merge sorted... I did push the parser
changes (https://github.com/denuno/cfml.parsing).
:den
--
Guys: No Shirt, No Service - Gals: No Shirt, No Charge
Den et al.,
I updated to the dev build (extremely excited about the strides you guys are making). And I am looking at an "all-script" component and not seeing any outline of methods view. I tried closing eclipse and starting -clean. I also closed the views and made sure I had the correct ones open.
Here is the version from help > about eclipse:
CFEclipse (including MXUnit and Frameworks) 1.4.5.201202261042 org.cfeclipse.cfml.feature.feature.group
Is it working for anyone else that has updated?
"An error has occurred. See error log for more details.
org.cfeclipse.cfml.views.cfcmethods.CFCMethodViewScriptItem cannot be cast to org.cfeclipse.cfml.views.cfcmethods.CFCMethodViewItem"
missing SEMICOLON at 'function' 0 cfml.parsing.cfscript.CFParseException JiraAPI.cfc /local DealerPeak/com/jira line 11
--
Yes, +1 for that idea.
Al
That'd definitely be sweet...