PB IDE plugin : smart indent, remove spaces, autocompletions

eddy · Post by **eddy** » Tue May 27, 2008 7:52 pm

1378 => CallNextHookEx(@pluginHook()....)

It will be very hard to debug this.

eddy · Post by **eddy** » Tue May 27, 2008 11:07 pm

[released v3.5b ]
- BUG FIX : simple hook ( break the hook chain to fix keyboard input bug :roll: )

Check this new option.
I hope it will fix your problem without any side effect

Idea for the next version :
- preview folded code
- drag'n drop folded code

eddy · Post by **eddy** » Sun Jun 01, 2008 2:17 pm

[released v3.6]
- ADDED: ticker cursor
- ADDED: indent guide
- ADDED: preview folded lines

Foz · Post by **Foz** » Fri Jun 06, 2008 1:47 pm

Could you add a spacing option for the + operator please?

I prefer to have my maths and string concatenations spread out

inc. · Post by **inc.** » Fri Jun 06, 2008 5:35 pm

Indeed this is a very nice work eddy!

eddy · Post by **eddy** » Sun Jun 08, 2008 7:57 pm

[released v3.7]
ADDED : spacing rules
UPDATED : automatic formatting (can format 'last opened files', files open at start of IDE)

Remark: you have to restart the installer, i changed some trigger parameters

eddy · Post by **eddy** » Wed Jun 11, 2008 8:49 pm

It would be interesting to replace the standard autocompletion list.

But perhaps this idea is too ambitious....
- need to know all keywords constants interfaces structures
- parse project files
- sort list

Foz · Post by **Foz** » Wed Jun 11, 2008 9:34 pm

As the IDE already has the autocomplete, what would be gained by having your own?

Is there some sort of super-duper-snazzy-wonderful plan behind your thinking?

eddy · Post by **eddy** » Wed Jun 11, 2008 11:03 pm

the autocompletion list is the last weak point of this IDE.
-> some bugs and missing features

But it's just an idea.

eddy · Post by **eddy** » Sat Jun 14, 2008 6:05 pm

[released v3.8]
ADDED : backspace unindents (like DELPHI)

Foz · Post by **Foz** » Sat Jun 14, 2008 8:12 pm

I don't know how much work is involved, so I don't know if you are biting off more than you can chew.

However, if you feeling up to replacing the autocomplete, I think you have an army of willing testers waiting to sample your work

oreopa · Post by **oreopa** » Sun Jun 22, 2008 10:35 am

Just wanted to express my appreciation for this add-on... had missed it up until now. Very very useful indeed. Good work and thanx!

Num3 · Post by **Num3** » Sun Jun 22, 2008 2:56 pm

Would be nice if you made the preferences file path relative...
It' very boring to have to open all purebasic preference file and edit them by hand

Code: Select all

d:\programing\PB4\IDETools\PBIicon.ico
to
PBIicon.ico

SofT MANiAC · Post by **SofT MANiAC** » Mon Jun 23, 2008 7:37 am

it looks ugly (Pure formatter AUTO):

Code: Select all

;	used here include 16,32,50, etc. The findPath procedure uses this
  ;	number to convert current and destination locations (see below)
  ;	to locations in the walkability array.
  ;	- startingX,startingY = location of the pathfinder (pixel based coordinates)
  ;	- targetX,targetY = location of the target destination (pixel based coordinates)
  
  ;	The findPath() procedure procedureReturns whether a path could be found (1) or
    ;	if it's nonexistent (2). If there is a path, it stores it in a bank
        ;	called pathBank(pathfinderID).
        
        ;2.	readPath(pathfinderID,currentX,currentY,tileSize,pixelsPerFrame)
        ; This procedure reads the path data generated by findPath() and procedureReturns
        ;	the x and y coordinates of the next step on the path. They are stored
        ;	as xPath(pathfinderID) and yPath(pathfinderID). These coordinates are
        ;	pixel coordinates on the screen. See the procedure for more info.
            ;	The parameters are:
            ;	- pathfinderID = same as above
            ;	- currentX,currentY = current location of pathfinder in pixel
            ;	based coordinates
            ;	- tileSize = same as above
            ;	- pixelsPerFrame = number of pixels traveled per frame. This info
            ;	is used by the path finder to determine how close to the center
            ;	of a square the pathFinder must get before it looks up the
          ;	next step on the path.
          
          ;3.	preProcessMap(mapWidth,mapHeight) = this procedure preprocesses
            ;	the map for faster pathfinding.
              
              ;Background (for those who want to understand the findPath() procedure)
              ;----------
              ;	The basic A* method is to begin at the starting location and search
              ;	adjacent squares with the lowest F costs (see below) until you find
              ;	the target. The path is then generated by working backwards from the
              ;	target to the starting location, moving from each square to its
              ;	adjacent "parent" square.
              
              ;	F = G + H
              ;	G = distance from starting location to a given square by
              ;	going along the path generated to get to there.
              ;	H = distance from the given square to the target square. This
              ;	is often referred to as the "heuristic" - an unnecessarily
              ;	confusing term in my opinion.
              
              ;	The best way to follow how A* works is to do a step-by-step
              ;	search in Demo #1
              
              Declare readPath(pathfinderID, currentX, currentY, tileSize, pixelsPerFrame)

eddy · Post by **eddy** » Mon Jun 23, 2008 9:47 am

I know...
I have this problem sometimes.

This is my main task for the next release