Author Topic: Group project  (Read 11456 times)

0 Members and 1 Guest are viewing this topic.

Mark

  • Custom Title
  • Seagull
  • Posts: 28753
Group project
« Reply #15 on: June 23, 2004, 12:59:14 PM »
I think we need to define our audience, when I first thought of this I was thinking about the end user of what ever program that includes our function when in fact I should have been thinking about the programmer who is going to included this function in his program.
TheSwamp.org  (serving the CAD community since 2003)

t-bear

  • Guest
Group project
« Reply #16 on: June 23, 2004, 01:08:03 PM »
Yah......leave the ol' Bear out in the cold....up a creek w/o a paddle....the un-bear, un-wanted, un-appreciated & un-derfed.....(sob!)

JohnK

  • Administrator
  • Seagull
  • Posts: 10605
Group project
« Reply #17 on: June 23, 2004, 01:12:37 PM »
I think our target audence shoule be old men who like to canoe. (whatda think?)

Mark, I think we are talking about a "standard" For every procedure we create we would need to read that file to get the users settings and set those values as their default. So lets say that instead of ...OMG! I think i might have an idea; Let me mull on this a sec.
TheSwamp.org (serving the CAD community since 2003)
Member location map - Add yourself

Donate to TheSwamp.org

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Group project
« Reply #18 on: June 23, 2004, 01:23:11 PM »
Quote from: Se7en
I think our target audence shoule be old men who like to canoe. (whatda think?)

I think most guys like a bit of canoe here and there. :)

Oh, did I share too much?
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

JohnK

  • Administrator
  • Seagull
  • Posts: 10605
Group project
« Reply #19 on: June 23, 2004, 02:00:12 PM »
lol. ummm, yep!

Here is what i was thinking about:

Lets take a general procedure idea of setting up layers in a drawing. (This might be a bad example but bear with me)

Lets say that the user has several diff main clients each with their own "standards" we could retrieve the file and read the layers and their settings from the drawing directory.  The application will work with multiple diff "clients" cause all they need is a file in that dir with values.

..ok that was a bad example.
TheSwamp.org (serving the CAD community since 2003)
Member location map - Add yourself

Donate to TheSwamp.org

Mark

  • Custom Title
  • Seagull
  • Posts: 28753
Group project
« Reply #20 on: June 23, 2004, 02:20:14 PM »
How about this for the specs?
This function will have the ability to read, write and replace variable values placed in a ascii file. The variable and value shall be separated by one '=', no spaces allowed on either side of the '='. All lines that begin with the comment character will be ignored.

function shall require three(3) arguments
        1) file name and path if needed
        2) what is the comment character
        3) what is the function going to do, i.e. read, write or replace a var.

Example:
Code: [Select]

(defun func (filename "#" "r" / local vars)
  ( .........
 )
TheSwamp.org  (serving the CAD community since 2003)

MP

  • Seagull
  • Posts: 17750
  • Have thousands of dwgs to process? Contact me.
Group project
« Reply #21 on: June 23, 2004, 03:54:39 PM »
My own inclination is to initially forgo the identification of any functions, instead defining the standard with regards to what type of data we wish to store, what kind of layering of that data might be required, and then determine what functionaility is required to retrieve and maintain the information hosted by the container as defined. This is frequently an iterative process.

However, given that the properties and methods often suggest what a container can host, perhaps a review of this info would serve as a starting point. :)
Engineering Technologist • CAD Automation Practitioner
Automation ▸ Design ▸ Drafting ▸ Document Control ▸ Client
cadanalyst@gmail.comhttp://cadanalyst.slack.comhttp://linkedin.com/in/cadanalyst

JohnK

  • Administrator
  • Seagull
  • Posts: 10605
Group project
« Reply #22 on: June 23, 2004, 06:44:21 PM »
Ok, Ok. I was thinking about this on my drive home. How about this: Keep it simple stupid Lets not worry about what the config file is for or its data. Lets work on a procedure to just write information to a ascii file.  Reason: Lets say that i had a big application that needed a config file or a storage file we should cerate a procedure to read and write to a file... My point is; I dont think we should wory about syntax, just let the programer worry about that.

(defun ConfigFileGen (file comment info value)
 ~open file~
 ~ add comment ~
 ~add info~ ~add value~
*recurse thru untill done*
)
TheSwamp.org (serving the CAD community since 2003)
Member location map - Add yourself

Donate to TheSwamp.org

rugaroo

  • Bull Frog
  • Posts: 378
  • The Other CAD Guy
Group project
« Reply #23 on: June 23, 2004, 07:45:29 PM »
Maybe I can help. Here is a little snippet from my dwgtrkr.lsp:

Code: [Select]
(defun configfilesetup ()
  (setq file (open "x:\\xxx\\config.asc" "a")
          empt (strcat "")
          firs (strcat "xxxxxxx" setting1 "")
          scnd (strcat "xxxxxxx" setting2 "")
          thir (strcat "xxxxxxx" setting3 "")
          )
  (write-line empt file)
  (write-line firs file)
  (write-line scnd file)
  (write-line thir file)
  (close file)
  (princ)
  )


Maybe it will help, and maybe not. figured i would try.
LDD06-09 | C3D 04-19 | Infraworks 360 | VS2012-VS2017

SMadsen

  • Guest
Group project
« Reply #24 on: June 24, 2004, 05:16:01 AM »
I would agree with Mr. Puckett. It's all about data. No data, no need.

What kind of data would you want to process and which facilities do you want to offer?
The coding is the easy part.

Mark

  • Custom Title
  • Seagull
  • Posts: 28753
Group project
« Reply #25 on: June 24, 2004, 09:59:14 AM »
>What kind of data would you want to process
variable=value

>which facilities do you want to offer?
read, write and modify

I hate to sound redundant but........, I guess I'm missing something here.  *mark is confused* :D
TheSwamp.org  (serving the CAD community since 2003)

SMadsen

  • Guest
Group project
« Reply #26 on: June 24, 2004, 10:51:27 AM »
Ok, then that's settled .. on with the coding :)

SMadsen

  • Guest
Group project
« Reply #27 on: June 24, 2004, 11:53:24 AM »
Quote from: Mark Thomas
>What kind of data would you want to process
variable=value

Would that be the only requirement? Should data be grouped? Conditional? Any special identification?

What I'm driving at could for example be a utility that reads a range of settings in a drawing where each kind of data could hold different attributes. For example, say you want to export layers, dimstyles and some system variables.

To identify a layer, you would have to deal with multiple values (or attributes), e.g.:
LAYER=name;color;ltype;lweight;plot

whereas system variables would simply be identified by name=value

Dimstyles could be enclosed in a special syntax:
[Dimstyle=name]
DIMSCALE=1.0
DIMEXE=2.0
DIMTXSTY=Standard
[Dimstyle]

And so on ...

Mark

  • Custom Title
  • Seagull
  • Posts: 28753
Group project
« Reply #28 on: June 24, 2004, 05:08:14 PM »
I'm not ignoring you Stig, I'm thinking ............ :D

I now understand what you and Michael where talking about. Sorry for being so........ um.... ignorant!!
TheSwamp.org  (serving the CAD community since 2003)

SMadsen

  • Guest
Group project
« Reply #29 on: June 24, 2004, 05:28:17 PM »
Thinking is good :)