Perlipse Development

1.0.2 released

2012-04-27T15:35:00.001-04:00

i'm pleased to announce the 1.0.2 release of perlipse.

here's what's new and noteworthy:

java 1.6 is now required
updated plugin versions to use a 'qualifier'
added 'branding' plugin
no longer uses deprecated dltk methods*
parser bug fixes and AST work
ppi4j parser is now the default parser on new installations
issue 26 has been fixed and a new preference introduced to set the color of back tick strings

the thing i am most excited about in this release though are the new icons provided by new project contributor, james lauer!

head on over to the project page for more details.

* the one exception to this is code folding which is going to require an entire re-write.

1.0.1 released

2012-04-17T12:49:00.001-04:00

i am pleased to announce the 1.0.1 release of perlipse. this release primarily deals with fixing issue 25 in addition to presenting include statements in the outline view.

at the moment, only 'use' statements are included in the view as i haven't quite figured out how best to distinguish the remaining types ('no' and 'require') in the tree.

i was thinking about either a text representation where 'u' is for 'use', 'n' is for 'no' and 'r' is for require, i.e. (yes, this is contrived):

  [u] strict

  [n] warnings

  [r] Data::Dumper

or a different image/icon, which of course, i would have to create and my image skills suck. :)

looking forward, my plan is to continue enhancing the AST while introducing new functionality that depends on it. currently i have my sites focus on some basic hyperlink support.

head on over to the project page for more details.

oh, one more thing, if you installed using the update-site, just tell eclipse to check for new updates and it should find the latest release.

debugger work around

2012-04-04T12:59:00.001-04:00

it would appear that the latest version of the dbgp implementation for perl does not work as expected. given that the dtlk implementation has not changed recently and that a much older copy still works, i am inclined to think there is a bug in the latest implementation or there was some kind of undocumented change.

i've reached out to the active state folks but until i get a response from them, there isn't much i can do.

however, there is a work around! i have made an older copy of the dbgp implemenation here, so if you install that, you should be good to go.

1.0.0 released

2012-04-02T14:16:00.001-04:00

stop the presses! after 2+ long years, i am pleased to announce that perlipse 1.0.0 has finally been released!!!

the 1.0.0 release brings perlipse in line with the 3.0 release of the dltk and also introduces initial support for a source parser based on ppi4j.

head on over to the project page for more details.

note: i just realized that i should probably include the caveat that there is not a lot of polish behind the source parser right now and it is possible that runtime exceptions could be thrown when parsing code. if you encounter this, please file a bug report and include a snippet of code that demonstrates the issue.

quick update

2012-02-28T17:49:00.001-05:00

just so no one thinks i fell off the face of the planet again...

i am happy to report that after some head banging, i have fully ported PPI's tokenizing logic and am well on my way with the parser, having finally figured out how to deal with this:

  if ( ref $Parent eq 'PPI::Statement' )
  {
      bless $Parent, 'PPI::Statement::Compound';
  }

in java.

the trick was to use a temporary object that i could store the class type on and then convert to that object before adding it to the overall document. with that hurdle out of the way, all that is left (i hope) is some straight forward logic porting.

it's still too soon to say when this will be ready, especially with an upcoming trip to amsterdam, but i'm really hoping for the end of march.

now where was i...

2012-02-08T10:44:00.001-05:00

it's interesting to go back and look at code one hasn't touched in 2+ years - i definitely had quite a few "uh, how does this work again" and "wtf was i thinking here" moments. good times! :)

now, where was i...

i've gone through and synced with the current head of dltk, which appears to be working on the 4.0 release. i did some quick testing (i wish i had better unit tests, but i don't fully understand how to break eclipse down into smaller pieces) and everything appears to be working as it should, or as much as has been implemented, which brings me right back to the parser issue.

perlipse is never truly going to be useful unless an AST of a perl source can be produced. i can make it the best debugger in the world, but without some of the features the editor provides (outline, hyperlinks, etc), well - there are other alternative (some not free) solutions available.

so…in order to deal with this problem, i have decided (well, actually i decided and started on..) to try and port PPI to java, and i'm happy to report that after getting past some bumps in the road, things are progressing quite well and when all is said and done, this should put perlipse well on it's way to becoming a useful editor as well. that's the good news…the bad news is it's a lot of work and i only have so many hours in my day that i am able to devote.

but hey, you've waited this long already, so what's a little longer, right? :)

happy 2012

2012-01-20T11:35:00.001-05:00

greetings and salutations in the year 2012! after a very, very long hiatus, development work on perlipse has resumed.

stay tuned for further updates!

news from the dead

2009-06-01T16:13:00.001-04:00

i realize it's been a while since any kind of update has been posted, and unfortunately it may be a little while longer before one is again. aside from having a crazy summer concert tour planned, i've had a couple other events occur in my life recently that have left me little time for anything else. but fear not, i am committed to continuing work on this project. once i return from bonnaroo things should calm down a bit, leaving me more time to focus my attention here.

any antlr experts out there?

2009-03-24T12:45:00.001-04:00

i'm having some difficulties getting my token building logic correct, anyone able to provide some assistance?

and now the news you've been waiting for

2009-03-16T21:47:00.002-04:00

*drum roll*

i am pleased to announce that a new source parser implementation has been created. i don't want to give too much away just yet incase it all blows up in my face - and it's 24 night, but all initial tests look good.

stay tuned!

'perl -c' support, round one

2009-03-04T12:52:00.002-05:00

basic support for compiling source code via the interpreter and reporting errors back in the gui has been added. check out the screen shot below.

i'm not sure why the problem marker isn't displaying in the outline view, which is something i'll have to investigate. the next step will be to add preference support so things like warnings and taint mode and be turned on and off.

in other news, i've encountered an annoying bug that causes any folded code that falls within the definition of a SourceModule to be quickly expanded and then refolded any time a save operation has been performed. i can't seem to replicate this issue in any of the other dltk plugins (except for python) so tracking down the problem should prove to be an aggravating experience. :)

code folding improvements

2009-02-11T15:59:00.001-05:00

after suffering many bouts of motivational deficiencies and general laziness on my part, i've gotten my act together and have finished off the code folding improvements i had been working on. here are a couple of screen shots of the new preference pages:

and here's an action shot of the editor:

it should be noted that source code folding is only going to work if you're using the experimental ppi parser. one of these days i swear i'm going to do something about the overall parser situation, but unfortunately that day is not today.

0.9.8 released

2008-11-19T15:18:00.002-05:00

hot off the compiler i present to you perlipse 0.9.8. some items of interest:

java 1.5 is now required
todo task tags
improved syntax highlighting
detail formatters for debugging

head on over to the project page for more details.

syntax highlighting improvements

2008-11-19T12:50:00.002-05:00

syntax highlighting improvements have landed, here's a list things that can now be highlighted:

keywords, barewords, and file handles
variables (arrays, hashes, scalars)
quote like/regular expression operators
package/subroutine name declarations

here's a quick screen shot of the highlighting in action:

i'm sure there are a plethora of edge cases that have yet to be discovered, so please feel free to file a bug report should you encounter one.

woo! first bug report

2008-11-06T17:37:00.003-05:00

well, it looks like there are people actually trying this thing out, as i received my first bug report.

in other news, project specific task tag support has been added:

and syntax validation (perl -c) is starting to come to life:

although there's still a lot of ground to be covered in that area.

status update

2008-09-29T21:52:00.001-04:00

it's been quite a while since i've posted anything... development continues, although at a much slower pace then i would like. blame life, the day job, general laziness, <insert excuse here>, although i'm still feeling somewhat lazy when it comes to blog posts, so this will be quick... things recently done: * initial task tag support * variable detail formatters things on the horizon: * compiling script resources on save (perl -c) * documentation hovers * partition/color scanner improvements stay tuned...

odds and ends

2008-07-20T14:27:00.001-04:00

i've been meaning to post this for quite some time, but have been lazy. news on new functionality and maybe a quick howto for adding that support to your plugin on the way. - remote breakpoint support has been added to the core, huzzah! - here's a great video that displays some of the features of the 0.95 release of the dltk using the tcl plugin. the topics discussed in the 'code editor/navigation/assist' sections don't all apply to perlipse yet, but some day...

the saga continues...

2008-06-24T22:38:00.001-04:00

with the 0.9.7 release behind us (well, me), i've decided to refocus my efforts on getting the remote breakpoint support working. i've grown tired of the debugging hell i have to suffer at the day job. just to recap the issue: if a resource from a remote debugging session is mapped back into the local workspace, there is a chance the location of that resource on the remote host does not match that of the local. if the location paths don't match, the debugging engine can't find the breakpoint. i thought i could get around this using marker data to swap out the paths right before the breakpoint is set, and we all know what happened to thought... that approach doesn't work for 'deferred' breakpoints (and potentially a bunch of other scenarios i came up with, but don't care to elaborate on), which makes debugging an embedded application quite hard. i've got a couple other ideas on where to go next, but that's another post, i'm tired. p.s. it looks like some of you are attempting to give the parser a whirl. i know it needs a lot of help, but i would like to hear about people's experiences thus far, especially on the installation part.

0.9.7 released

2008-06-22T18:09:00.002-04:00

just in time for the ganymede release, i give you perlipse 0.9.7. check out the project page for more details. this release also introduces the experimental ppi parser i've been working on - and when i say experimental, i mean experimental, so expect things not to work properly or at all in some cases. it should also be noted that performance becomes notably worse for larger and more complex scripts/modules, so mileage will vary at this point. here's a screen shot of a simple module in the editor with its outline view displayed and the $foo variable selected in both.

check out the installation notes for how to get up and running with the parser.

quick update

2008-06-03T21:33:00.001-04:00

it's been a while since i've posted something, but rest assured, work still continues however progress is slow due to work load at the day job, warmer weather activities, and some minor laziness. :) the next release will occur shortly after the 0.9.5 dltk release, hopefully along with the extremely experimental parser implementation.

huzzah!

2008-04-01T22:43:00.001-04:00

there's still some work to be done, but i just finished adding support to select which installed interpreter should be used to execute the source parser script.

coupled with a recent upload to cpan, look what works under windows now:

that's right - a working parser under cygwin's perl. huzzah!

0.9.6 released

2008-03-15T15:04:00.001-04:00

i'm happy to announce that perlipse 0.9.6 (0.9.5 was never publicly released) is now available. you will need to install the 2008.03.14 dltk integration build for things to work properly, but i'd imagine that if you're trying this plugin out, you're willing to live on the edge. check out the project page for installation instructions. i've come to the conclusion that this plugin is never really going to be useful with some kind of source parser, and time is going to be spent in that area. i may also go back and see what can be done about the remote debugging limitations because having this working would be quite beneficial for some of my current day job tasks.

search added

2008-03-09T19:17:00.001-04:00

it's been a busy past few days :) search support has been added:

although it's only really useful with a working parser implementation, and i haven't released one of those yet. :) i enabled this for the dltk python plugin as well, but it doesn't seem to work for some reason. i think there is an issue with how the source files are being indexed, but that could be incorrect. i'm surprised the perl implementation worked more or less 'out of the box. edit: helps to use the right images :)

template support

2008-03-09T18:19:00.001-04:00

i've never really used this functionality much, but it was pretty easy to do, and since i have delayed my venture into common navigator space (more on that later, maybe...for now it's in a holding pattern) i've decided to start adding functionality to make the editor portion more useful.

one note about the shebang template support - it only works correctly if you use it on a blank line (just invoke the auto complete sequence for the window to appear). see here if you're interested in the details. if anyone wants to contribute templates, let me know. p.s. the dltk python plugin has template support now as well.

debugging engine logging support

2008-03-09T18:05:00.001-04:00

now you can get logging information from the active state debugging engine - woohoo!