From: Francesco <fra...@gm...> - 2010-03-24 20:55:05
|
Hi Frans/all, I wonder if it wouldn't be a good idea to ship with upp_wx a couple examples of PIC projects which: 1) could be used by new users to get started with the PIC world and usbpicprog itself 2) could be used as quick test for us to check if usbpicprog works well with a certain PIC I think it should not be too difficult to create a couple projects suitable (with very small modifications) to cover a wide range of PIC devices (e.g. a small program which blinks a LED). I'd also include both Piklab and MPLAB project files and the .hex files (so that users without piklab or MPLAB can immediately test their usbpicprog ;)). Just my 2 cents, Francesco |
From: Frans S. <fra...@gm...> - 2010-03-25 07:42:50
|
Hi Francesco, I this is a very good idea, but maybe also a community thing to do. I think I can make a few examples with different compilers, but shall I make a page on the website with a submit form or something like that in order to be able to have contributions from the community? I think it would be good to also deliver some example schematics. For that we will need a standard tool - shall we suggest KiCad for that? I will give it a shot! Frans On 3/24/2010 21:55, Francesco wrote: > Hi Frans/all, > I wonder if it wouldn't be a good idea to ship with upp_wx a couple > examples of PIC projects which: > 1) could be used by new users to get started with the PIC world and > usbpicprog itself > 2) could be used as quick test for us to check if usbpicprog works > well with a certain PIC > > I think it should not be too difficult to create a couple projects > suitable (with very small modifications) to cover a wide range of PIC > devices (e.g. a small program which blinks a LED). I'd also include > both Piklab and MPLAB project files and the .hex files (so that users > without piklab or MPLAB can immediately test their usbpicprog ;)). > > Just my 2 cents, > Francesco > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |
From: Francesco <f18...@ya...> - 2010-03-25 22:31:39
|
Hi Frans, 2010/3/25 Frans Schreuder <fra...@gm...>: > I this is a very good idea, but maybe also a community thing to do. I > think I can make a few examples with different compilers, but shall I > make a page on the website with a submit form or something like that in > order to be able to have contributions from the community? well, I was proposing to add just a couple examples very very simple (and thus portable among many PICs and easy to realize on e.g. breadboards for quick tests)... community inputs may be useful to build something different like a collection of hobbyst PIC projects. I think that it could be a good start to add a few small examples and add a notice on the website that user projects (of limited complexity) are welcome and can be posted on this mailing list (I don't think forms are well-suited for posting multiple files / code). Then we'll see how many users propose their projects and eventually develop more appropriate features for sharing user pic projects ;) One thing to consider however is that the more code we add to the repo the more code we have to maintain, comment, fix, etc. So simply adding everything we can add may not be the best choice. > I think it would be good to also deliver some example schematics. yes, good idea, although what I had in mind was to require as less hw as possible (e.g. an R+C for the PIC oscillator and a R+LED for blinking) and thus a schematic maybe not be so much necessary. But adding it would of course be a plus. > For > that we will need a standard tool - shall we suggest KiCad for that? Personally I always use Cadsoft EAGLE for schematics and layouts and MicroCap for simulations (yes I know: neither of them is open-source :/ but free student/limited versions are available for both) . I used Kicad only for opening usbpicprog schematics but I've found it a bit messy (icons not clear, menus partially translated and partially not, and often translated wrong, commands uncomfortable to use, redrawing not always working, etc). Nonetheless given that the schematics should be very simple I think it would be ok to go with KiCad... > I will give it a shot! great! Francesco PS: I can provide the MPLAB versions of the projects if you need. |
From: Francesco <f18...@ya...> - 2010-04-13 21:56:33
|
Hi Frans, as you may have noticed I've added a small test PIC project to the usbpicprog folder as previously discussed... I noticed only after that there is now a specific page for the projects on the usbpicprog.org website :) However I think it would be nice to have the projects installed together with the upp software and have a dedicated "File -> Open example" command just below "File -> Open"... what do you think? Should we add the dice project to the SVN too and update the installers? Francesco 2010/3/25 Francesco <f18...@ya...>: > Hi Frans, > > 2010/3/25 Frans Schreuder <fra...@gm...>: >> I this is a very good idea, but maybe also a community thing to do. I >> think I can make a few examples with different compilers, but shall I >> make a page on the website with a submit form or something like that in >> order to be able to have contributions from the community? > well, I was proposing to add just a couple examples very very simple > (and thus portable among many PICs and easy to realize on e.g. > breadboards for quick tests)... community inputs may be useful to > build something different like a collection of hobbyst PIC projects. I > think that it could be a good start to add a few small examples and > add a notice on the website that user projects (of limited complexity) > are welcome and can be posted on this mailing list (I don't think > forms are well-suited for posting multiple files / code). > Then we'll see how many users propose their projects and eventually > develop more appropriate features for sharing user pic projects ;) > > One thing to consider however is that the more code we add to the repo > the more code we have to maintain, comment, fix, etc. So simply adding > everything we can add may not be the best choice. > >> I think it would be good to also deliver some example schematics. > yes, good idea, although what I had in mind was to require as less hw > as possible (e.g. an R+C for the PIC oscillator and a R+LED for > blinking) and thus a schematic maybe not be so much necessary. But > adding it would of course be a plus. > >> For >> that we will need a standard tool - shall we suggest KiCad for that? > Personally I always use Cadsoft EAGLE for schematics and layouts and > MicroCap for simulations (yes I know: neither of them is open-source > :/ but free student/limited versions are available for both) . I used > Kicad only for opening usbpicprog schematics but I've found it a bit > messy (icons not clear, menus partially translated and partially not, > and often translated wrong, commands uncomfortable to use, redrawing > not always working, etc). > Nonetheless given that the schematics should be very simple I think it > would be ok to go with KiCad... > >> I will give it a shot! > great! > > Francesco > > PS: I can provide the MPLAB versions of the projects if you need. > |
From: Frans S. <fra...@gm...> - 2010-04-14 06:33:09
Attachments:
signature.asc
|
Hi Francesco, I think it's nice to put the files in the installer, but I think it would be better to have a menu item that just opens a nautilus / explorer / finder to wherever the examples are. Since there are not only .hex files in that folder it would be good to show the people that there is more than just the .hex file. Yes, let's add the dice project as well, I was planning to do so anyway, but I just found this nice example somewhere on a computer where I didn't have an svn client installed... Frans On 4/13/2010 23:56, Francesco wrote: > s you may have noticed I've added a small test PIC project to the > usbpicprog folder as previously discussed... I noticed only after that > there is now a specific page for the projects on the usbpicprog.org > website :) > > However I think it would be nice to have the projects installed > together with the upp software and have a dedicated "File -> Open > example" command just below "File -> Open"... what do you think? > > Should we add the dice project to the SVN too and update the installers? > > Francesco > |
From: Francesco <f18...@ya...> - 2010-04-14 22:22:59
|
Hi, 2010/4/14 Frans Schreuder <fra...@gm...>: > I think it's nice to put the files in the installer, but I think it > would be better to have a menu item that just opens a nautilus / > explorer / finder to wherever the examples are. > Since there are not only .hex files in that folder it would be good to > show the people that there is more than just the .hex file. well, it would strange for me (as a user) to click File -> Open Example and be redirected to the standard file explorer/nautilus/finder; as user I should first understand that the explorer which has been launched is a wanted effect and second that I should rather use "File -> Open" command, browse to the example folder and finally select the .hex file to "really" open the example in the upp_wx application... what about adding both - a File->Open example which always open the standard "file open" dialog in the examples folder installed together with upp_wx (and lets you select a .hex) and - an Help->Examples menu which always open the examples folder in the standard file explorer/nautilus/finder; ? > Yes, let's add the dice project as well, I was planning to do so anyway, > but I just found this nice example somewhere on a computer where I > didn't have an svn client installed... ok, nice! Francesco |
From: Frans S. <fra...@gm...> - 2010-04-20 11:49:53
Attachments:
signature.asc
|
I have implemented the menu item in the application, as well as adding the Makefiles to automatically install the examples on linux and osx. Frans On 4/15/2010 12:22 AM, Francesco wrote: > Hi, > > 2010/4/14 Frans Schreuder <fra...@gm...>: > >> I think it's nice to put the files in the installer, but I think it >> would be better to have a menu item that just opens a nautilus / >> explorer / finder to wherever the examples are. >> Since there are not only .hex files in that folder it would be good to >> show the people that there is more than just the .hex file. >> > well, it would strange for me (as a user) to click File -> Open > Example and be redirected to the standard file > explorer/nautilus/finder; as user I should first understand that the > explorer which has been launched is a wanted effect and second that I > should rather use "File -> Open" command, browse to the example folder > and finally select the .hex file to "really" open the example in the > upp_wx application... > > what about adding both > - a File->Open example which always open the standard "file open" > dialog in the examples folder installed together with upp_wx (and lets > you select a .hex) > and > - an Help->Examples menu which always open the examples folder in the > standard file explorer/nautilus/finder; > ? > > >> Yes, let's add the dice project as well, I was planning to do so anyway, >> but I just found this nice example somewhere on a computer where I >> didn't have an svn client installed... >> > ok, nice! > > Francesco > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |